What is the purpose of the change

• We've concluded a hook-based approach to protorev will be the best approach to keep protorev up to date given several new message types being introduced that allow for swaps.
• Previously, protorev would case on specific message types for a transaction, and extract the pools that were swapped against to check for backrun potential.
• This PR changes this approach to now plug protorev into the GAMM and Concentrated liquidity hooks, store the necessary swap information in the hook, and then read from that store in the protorev posthandler.
• We also add logic to support join/exit pool hooks for the GAMM module (treating single sided joins/exits as swaps), and pool creation (updating highest liquidity pools at creation of a new pool)

Brief Changelog

• Add new kvstore for SwapsToBackrun and add setters and getters
• Add hooks.go file that plugs into GAMM and ConcratedLiquidity pool hooks and stores/updates necessary protorev kvstores as appropriate based on the hook
  • Add SwapsToBackrun when triggered by a swap hook or join/exit pool hook that also swaps
  • Update highest liquidity pools at pool creation for GAMM and at initial liquidity position for CL (triggered by hook)
• Add SwapsToBackrun delete logic in postahandler without using gas

Testing and Verifying

• New tests added for all protorev hook logic in hooks_test.go
• Updated previous tests to use updated methods and no longer rely on messages as input
• Updated epoch_hook_test.go to account for new concentrated liquidity pool testing changes that sets default coins when creating a pool with a position range

Documentation and Release Note

• Added changelog entry